Multi-device architecture for tracking device access

ABSTRACT

A tracking server stores information identifying one or more community mobile devices and information identifying one or more tracking devices within a proximity of each of the one or more community mobile devices. The tracking server receives a tracking device request from a mobile device. The tracking device request includes information identifying a tracking device and configuration instructions for configuring the tracking device. The tracking server identifies a community mobile device from the one or more community mobile devices within a proximity of the tracking device. The tracking server sends the tracking device request to the identified community mobile device. The identified community mobile device is configured to forward the tracking device request to the tracking device and the tracking device is configured to re-configure the tracking device based on the configuration instructions included in the tracking device request.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.14/882,022, filed Oct. 13, 2015, which is incorporated herein byreference in its entirety.

BACKGROUND 1. Field of the Disclosure

This disclosure relates generally to communicating with a trackingdevice, and more specifically, to communicating with a tracking devicevia a connected device.

2. Description of the Related Art

Electronic tracking devices have created numerous ways for people totrack the locations of people and/or objects. For example, a user canuse GPS technology to communicate with a device remotely or determine alocation of the user. In another example, a user can attach a trackingdevice to an important object, such as keys or a wallet, and use thefeatures of the tracking device to more quickly communicate with theobject, (e.g., if it becomes lost).

However, traditional tracking devices and corresponding systems sufferfrom one or more disadvantages. For example, communicating with atracking device from a far-away distance requires a considerable amountof power. Thus, battery life of a tracking device is often limited.Further, technology for long-range communication is expensive, and oftenrequires sophisticated circuitry for operating in connection with anassociated electronic device (e.g., a mobile device). Additionally,low-power options for tracking devices are limited to communicating withnearby objects that require a user associated with the tracking devicesto be within a close proximity of the tracking devices, limiting theusefulness of such tracking devices.

SUMMARY

Embodiments relate to a tracking server. The tracking server storesinformation identifying one or more community mobile devices andinformation identifying one or more tracking devices within a proximityof each of the one or more community mobile devices. The tracking serverreceives a tracking device request from a mobile device. The trackingdevice request includes information identifying a tracking device andconfiguration instructions for configuring the tracking device. Thetracking server identifies a community mobile device from the one ormore community mobile devices within a proximity of the tracking device.The tracking server sends the tracking device request to the identifiedcommunity mobile device. The identified community mobile device isconfigured to forward the tracking device request to the tracking deviceand the tracking device is configured to re-configure the trackingdevice based on the configuration instructions included in the trackingdevice request.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an environment for use in locating a tracking deviceaccording to principles described herein.

FIG. 2 illustrates a tracking system of the environment of FIG. 1,according to one embodiment.

FIG. 3 illustrates a mobile device of the environment of FIG. 1,according to one embodiment.

FIG. 4 illustrates a community mobile device of the environment of FIG.1, according to one embodiment.

FIG. 5A illustrates a process of communicating with a tracking device,according to one embodiment.

FIG. 5B illustrates a process of communicating with a tracking device,according to another embodiment.

The figures depict various embodiments for purposes of illustrationonly. One skilled in the art will readily recognize from the followingdiscussion that alternative embodiments of the structures and methodsillustrated herein may be employed without departing from the principlesdescribed herein.

DETAILED DESCRIPTION

Embodiments described herein provide a user with the ability to locateone or more low-power tracking devices by leveraging the capabilities ofa mobile device associated with a community of users (e.g., users of thesame tracking device system) in a secure and privacy-focusedenvironment.

A user can attach a tracking device to or enclose the tracking devicewithin an object, such as a wallet, keys, a car, a bike, a pet, or anyother object that the user wants to track. The user can then use amobile device (e.g., via a software application installed on the mobiledevice) to communicate with the tracking device and the correspondingobject. For example, the mobile device can perform a local search for atracking device attached to a near-by object. However, in situationswhere the user is unable to locate the tracking device using their ownmobile device (e.g., if the tracking device is beyond a distance withinwhich the mobile device and the tracking device can communicate), theprinciples described herein allow the user to leverage the capabilitiesof another user of a tracking system (a “community user” hereinafter).

In particular, a tracking system (also referred to herein as a “cloudserver” or simply “server”) can associate a tracking device to one ormore community mobile devices (other devices of other users associatedwith the tracking system) within a threshold proximity of the trackingdevice. If the user's tracking device is out of range of the user'smobile device, the user can send a tracking device request to thetracking system, which is in communication with one or more mobiledevices associated with the community of users in communication with thesystem. The tracking system identifies a community mobile device withina threshold proximity to the tracking device and sends the trackingdevice request to the community mobile device which in turn sends thetracking device request to the tracking device. The tracking systemsends the tracking device request received by the user to the trackingdevice via the community mobile device, thereby enabling the user tocommunicate with the tracking device.

Environment Overview

FIG. 1 illustrates an environment for use in locating a tracking device106. FIG. 1 illustrates a tracking system 100 communicatively coupled toa mobile device 102 associated with a user 103 and a plurality ofcommunity mobile devices 104 a through 104 n (collectively referred toherein as “community mobile devices 104”) associated with a plurality ofusers 105 a through 105 n of the tracking system 100 (collectivelyreferred to herein as “community users 105”). As will be explained inmore detail below, the tracking system 100 allows the user 103 tocommunicate with the tracking device 106 associated with the user 103.In some embodiments, the tracking system 100 leverages the capabilitiesof the community mobile devices 104 to send a tracking device request tothe tracking device 106 if the tracking device 106 is not within athreshold proximity of the mobile device 102. In some configurations,the user 103 can own and register multiple tracking devices 106.Although FIG. 1 illustrates a particular arrangement of the trackingsystem 100, the mobile device 102, the community mobile devices 104, andthe tracking device 106, various additional arrangements are possible.

In some configurations, the user 103 can be part of the community ofusers 105. Further, one or more users of the community of users 105 canown and register one or more tracking devices 106. Thus, any one of theusers within the community of users 105 can communicate with thetracking system 100 and leverage the capabilities of the other communityof users 105 in addition to the user 103 to communicate with a trackingdevice 106.

The tracking system 100, the mobile device 102 and the community mobiledevices 104 communicate via a first network 108. The tracking system100, the mobile device 102 and the community mobile devices 104 cancommunicate using any communication platforms and technologies suitablefor transporting data and/or communication signals, including knowncommunication technologies, devices, media, and protocols supportive ofremote data communications. The first network 108 can include one ormore networks, including, but not limited to, wireless networks (e.g.,wireless communication networks), mobile telephone networks (e.g.,cellular telephone networks), closed communication networks, opencommunication networks, satellite networks, navigation networks,broadband networks, narrowband networks, the Internet, local areanetworks, and any other networks capable of carrying data and/orcommunications signals between the tracking system 100, the mobiledevice 102, and the community mobile devices 104.

The mobile device 102 and the community of mobile devices 104 cancommunicate with a tracking device 106 via a second network 110. Thesecond network 110 can be a similar or different type of network as thefirst network 108. In some embodiments, the second network 110 includesa wireless network with a limited communication range, such as aBluetooth or Bluetooth Low Energy (BLE) wireless network. In someconfigurations, the second network 110 is a point-to-point networkincluding the tracking device 106 and one or more mobile devices (e.g.,the mobile device 102 and the community of mobile devices 104) within athreshold proximity of the tracking device 106. Accordingly, any givenmobile device (such as the mobile device 102 and the community mobiledevices 104) is only able to communicate with the tracking device 106 ifit is within a threshold proximity to the tracking device 106. In someconfigurations, the mobile device 102 and one or more of the communitymobile devices 104 can each be associated with multiple tracking devices106 associated with various users (e.g., the user 103 and the communityof users 105).

As noted above, FIG. 1 illustrates the mobile device 102 associated withthe user 103. The mobile device 102 can be configured to perform one ormore functions described herein with respect to communicating withtracking devices (e.g., tracking device 106). For example, the mobiledevice 102 receives input from the user 103 representative ofinformation about the user 103, information about a tracking device 106,and a tracking device request (described below) to be sent to thetracking device 106. The mobile device 102 sends the tracking devicerequest to the tracking device 106 via the first network 108 or thesecond network 110. In some configurations, the mobile device 102 cannotsend the tracking device request to the tracking device 106 via thesecond network, for example, due to hardware limitations of the mobiledevice 102 (such as the tracking device 106 being located more than athreshold distance away from the mobile device 102). In suchconfigurations, the mobile device 102 sends the tracking device requestto the tracking device 106 via the first network 108.

In some embodiments, the mobile device 102 determines that the trackingdevice 106 is within a threshold proximity of the mobile device 102 viathe second network 110. The mobile device 102 enables the user 103 tocommunicate with the detected tracking device 106. For example, themobile device 102 receives user input from the user 103 (e.g., via anapplication executing on the mobile device 102 and/or an interactivegraphical user interface displayed by the mobile device 102 to the user103), requesting the mobile device 102 send a tracking device request tothe tracking device 106. In response, the mobile device 102 sends thetracking device request to the tracking device 106. The mobile device102 can notify the user that the tracking device request wassuccessfully received by the tracking device 106, for instance inresponse to a confirmation signal received from the tracking device 106.

In other embodiments, the mobile device 102 determines that the trackingdevice 106 is located outside a threshold proximity of the mobile device102. That is, the mobile device 102 is located beyond the immediaterange of communication with the tracking device 106 (e.g., beyond thecommunicative distance capabilities of the second network 110). In suchembodiments, the mobile device 102 enables the user 103 to communicatewith the tracking device 106 via the first network 110. For example, themobile device 102 sends the received tracking device request to thetracking system 100 via the first network 108, which in turn routes therequest to one or more community mobile devices 104 for forwarding tothe tracking device 106 (if the one or more community mobile devices 104are within a threshold proximity to the tracking device 106). The mobiledevice 102 can receive a confirmation signal from the tracking system100 indicating the tracking device request was successfully received bythe tracking device 106 via a community device 104. The mobile device102 can notify the user the tracking device request was successfullyreceived by the tracking device 106.

As used herein, a “tracking device request” refers to any communicationsent to the tracking device 106. In some embodiments, tracking devicerequests can include requests for the performance of a function by atracking device. In some configurations, the tracking device requestincludes instructions for the tracking device 106 to emit a sound orsong from a speaker of the tracking device 106. The tracking devicerequest can additionally include instructions for the tracking device106 to emit light from a light emitting diode (LED), to display anindication on a tracking device display, or to display or emit any othertype of notification (such as vibrations).

In addition, the tracking device request can include configurationinformation for the tracking device 106. The configuration informationcan include a list of users and/or mobile devices to add to a list ofverified users/devices stored by the tracking device. In suchembodiments, users and/or mobile devices on the verified list stored bythe tracking device 106 can communicate with the tracking device 106,can send tracking device requests to the tracking device 106, and canotherwise interact with or configure the tracking device 106. Theconfiguration information can further include a list of users and/ormobile devices to remove from a list of verified users/devices stored onthe tracking device. Other configuration information includes beaconsignal frequency, power settings, and enabling/disabling differentsensors.

The tracking system 100 can be configured to provide a number offeatures and services associated with communication between one or moretracking devices 106, and/or one or more associated users 103, 105. Forexample, the tracking system 100 can manage information and/or userprofiles associated with the user 103, the community users 105, and thetracking devices 106. In particular, the tracking system 100 can manageinformation associated with the tracking device 106 and/or othertracking devices associated with or within a threshold proximity of theuser 103 and the community users 105, and the mobile device 102 andcommunity mobile devices 104, respectively. The tracking system 100 isconfigured to receive, store, and transmit user information, trackingdevice information, tracking device requests, and/or information aboutthe mobile device 102 and the community of mobile devices 104. Thetracking system 100 additionally receives tracking device informationassociated with the tracking device 106 from any community mobiledevices 104 within a threshold proximity of the tracking device 106. Thetracking system 100 is able to associate the mobile device 102, the user103, and/or the tracking device 106, and to transmit the tracking devicerequest from the mobile device 102 to the tracking device 106 via thefirst network 108 and any community mobile devices 104 within athreshold proximity of the tracking device 106. That is, the trackingsystem 100 leverages the capabilities of the community mobile devices104 near the tracking device 106 to send the tracking device request tothe tracking device 106.

As shown in FIG. 1 and as noted above, the tracking system 100communicates with a plurality of community mobile devices 104 associatedwith corresponding community users 105. For example, an implementationcan include a first community mobile device 104 a associated with afirst community user 105 a, a second community mobile device 104 bassociated with a second community user 105 b, and additionalcommunication mobile devices associated with additional community usersup to an nth community mobile device 104 n associated with an nthcommunity user 105 n. The community mobile devices 104 can also includefunctionality that enables each community mobile device 104 to identifya tracking device 106 within a threshold proximity of the communitymobile device 104. In one example, a first community mobile device 104 awithin a threshold proximity of a tracking device 106 can identify thetracking device 106 (e.g., using a unique identifier associated with andtransmitted by the tracking device 106) and can communicate theidentification of the tracking device 106 to the tracking system 100,which in turn can store the association between the community mobiledevice 104 a and the tracking device 106, along with (for example) atimestamp indicating the time that the community mobile device 104 adetected the tracking device 106, a distance from the community mobiledevice 104 a to the tracking device 106, and the like. This informationcan be used by the tracking system 100 to identify a community mobiledevice 104 located within a threshold proximity to the tracking device106. In some embodiments, the tracking system 100 can identify aplurality of community mobile devices 104 located within a thresholdproximity to the tracking device 106, and can select the communitymobile device 104 associated with the most recent time of detecting thetracking device 106, the closest distance to the tracking device 106, orany suitable factor. In some embodiments, the steps performed by thefirst community mobile device 104 a (for instance, the detection of thetracking device 106) can be hidden from the first community user 105 a.Accordingly, the first community mobile device 104 a can detect and cantransmit a tracking device request to the tracking device 106 withoutbothering and without the knowledge of the first community user 105 a,thereby ensuring the privacy of the owner of the tracking device 106 andimproving the experience of the user 105 a.

As noted above, the tracking system 100 can assist the user 103 intransmitting a tracking device request to the tracking device 106outside of the range of the mobile device 102. The tracking device 106can be a chip, tile, tag, or other device for housing circuitry and thatcan be attached to or enclosed within an object such as a wallet, keys,purse, car, pet, or other object that the user 103 may track.Additionally, the tracking device 106 can include a transmitter forbroadcasting signals (such as beacon signals), and a receiver forreceiving communications (such as tracking device requests). In oneconfiguration, the tracking device 106 can periodically or in responseto an event (such as a detected motion of the tracking device 106)transmit a beacon signal that can be detected using a nearby mobiledevice 102 and/or community mobile device 104. The strength of thesignal emitted from the tracking device 106 can be used to determine adistance between the tracking device 106 and the mobile device 102 orcommunity mobile devices 104 that detects the signal. In some cases, thestrength of signal or absence of a signal may be used to indicate thatthe tracking device 106 is not within a threshold proximity of a mobiledevice (e.g., mobile device 102 and community mobile device 104).

In some configurations, the environment illustrated in FIG. 1 does notinclude the tracking system 100. In such configurations, the mobiledevice 102 sends a tracking device request to one or more communitymobile devices 104 connected via the first network 108 and/or the secondnetwork 100. The tracking device request includes a tracking device IDidentifying a tracking device 106. The one or more community mobiledevices 104 within a threshold proximity of the tracking device 106 sendthe tracking device request to the tracking device 106. The one or morecommunity mobile devices 104 receive a confirmation signal from thetracking device 106 indicating successful receipt of the tracking devicerequest, and forward the confirmation to the mobile device 102.

System Overview

FIG. 2 illustrates a diagram showing example components of the trackingsystem 100. As shown, the tracking system 100 includes, but is notlimited to, an association manager 204, a tracking device requestmanager 206, and a data manager 208 (herein collectively referred to as“managers 204-208”), each of which can communicate using any suitablecommunication technologies. It will be recognized that although managers204-208 are shown to be separate in FIG. 2, any of the managers 204-208can be combined into fewer managers, such as into a single manager, ordivided into more managers as can serve a particular embodiment. Thetracking system 100 can be a server, such as a cloud server, a datacenter, a computer specially configured to perform the functionalitiesdescribed herein, or any other suitable system.

The association manager 204 receives and processes information about oneor more specific tracking devices 106 within a threshold proximity ofone or more community mobile devices 104 configured to scan for nearbytracking devices 106. The association manager 204 stores the receivedinformation in a database (e.g., tracker database 212). In someconfigurations, the association manager 204 associates the trackingdevices 106 with the one or more community mobile devices 104. Forexample, the association manager 204 can store information about thetracking device 106, such as a tracking device identifier (ID) inassociation with an identifier for each of one or more community mobiledevices 104 within a threshold proximity of the tracking device 106.

In some configurations, the association manager 204 receives informationabout the tracking device 106 within a threshold proximity of the one ormore community mobile devices 104 and determines the tracking device 106has a pending tracking device request from the mobile device 102 whenupdating the database (e.g., tracker database 212). The associationmanager 204 identifies the one or more community mobile devices 104within a threshold proximity of the tracking device 106 and provides theinformation about the association (such as a tracking device ID, an IDfor each of the identified community mobile devices 104, etc.) to thetracking device request manager 206.

The tracking device request manager 206 (hereinafter referred to as“request manager 206”) receives, processes, and transmits trackingdevice requests from the mobile device 102 to the tracking device 106via the community mobile devices 104 within a threshold proximity of thetracking device 106.

In one example, the request manager 206 receives the tracking devicerequests from the mobile device 102. In response, the request manager206 queries a database (e.g., tracker database 212) and identifies oneor more community mobile devices 104 within a threshold proximity of thetracking device 106. In some configurations, the request manager 206queries the database using a tracking device ID associated with thetracking device request to identify the community mobile devices 104within a threshold proximity of the tracking device 106. The requestmanager 206 sends the received tracking device request to the one ormore identified community mobile devices 104 within a thresholdproximity of the tracking device 106. The request manager 206 canreceive a confirmation from the one or more community mobile devices 104indicating the tracking device 106 successfully received the trackingdevice request, and can forward the confirmation to the mobile device103.

In another example, the request manager 206 stores the tracking devicerequest. The request manager 206 can set a flag in a database (e.g.,tracker database 212) indicating that the tracking device 106 has apending tracking device request. Setting a flag for a tracking device106 can include storing and/or associating a value associated with thetracking device 106 that indicates that the tracking device 106 has apending tracking device request. This can include setting a flag,marker, digital value, or other indication that the tracking device 106has a pending tracking device request and maintaining or storing theindication of the associated tracking device 106 on the tracking system100 (e.g., on a database). In response to the receipt by the associationmanager 204 of a signal from a community mobile device 104 indicatingthat the community mobile device 104 is within a threshold proximity ofthe tracking device 106, the association manager 204 can query therequest manager 206 to determine if a flag indicating a pending trackingdevice request is set for the tracking device 106. In response to such adetermination, the tracking device request manager 206 can forward thetracking device request to the community mobile device 104 as notedabove. Upon receiving a confirmation signal indicating that the trackingdevice 106 has received the tracking device request (or in response toforwarding the tracking device request to the community mobile device104), the request manager 206 can remove the flag in the databaseindicating the tracking device 106 has a pending tracking devicerequest.

The data manager 208 stores and manages information associated withusers, mobile devices, tracking devices, tracking device requests andother data that can be stored and/or maintained in a database related totracking device requests. As shown, the data manager 208 may include,but is not limited to, a user database 210, a tracker database 212,permissions database 214, and communication request database 216. Itwill be recognized that although databases and data within the datamanager 208 are shown to be separate in FIG. 2, any of the user database210, the tracker database 212, the permissions database 214, and thetracking device request database 216 may be combined in a singledatabase or manager, or divided into more databases or managers as mayserve a particular embodiment.

The user database 210 stores data related to various users. For example,the user database 210 can include data about the user 103 as well asdata about each user 105 in a community of users 105. The community ofusers 105 can include any user that has provided user information to thetracking system 100 via a mobile device 102, 104 or other electronicdevice. The user information can be associated with one or morerespective tracking devices 106, or can be stored without an associationto a particular tracking device 106. For example, a community user 105can provide user information and permit performance of trackingfunctions on the community mobile device 104 without owning or beingassociated with a tracking device 106. The user database 210 can alsoinclude information about one or more mobile devices 102, 104 or otherelectronic devices associated with a particular user 103, 105.

The tracker database 212 can be used to store data related to trackingdevices 106 and community mobile devices 104. For example, the trackerdatabase 212 can include tracking data for any tracking device 106 thathas been registered with the tracking system 100. Tracking data caninclude unique tracking device IDs associated with individual trackingdevices 106. The tracking device IDs can be associated with one or morecommunity mobile devices 104 within a threshold proximity of thetracking device 106. Additionally, the tracker database 212 can includeany flags or other indications that the tracking device 106 has apending tracking device request.

The permissions database 214 can include information describingpermissions and permission levels associated with a particular user 103and/or tracking device 106. For example, the permissions database 214can identify additional users 105 with shared permissions (such asaccess permissions, communication permissions, and the like) for atracking device 106. The tracking device request database 216 caninclude information related to the tracking device request received fromthe user 103 via a mobile device 102, such as pending tracking devicerequest flags, times of receipt of the tracking device requests,identities of the user and/or mobile device associated with the trackingdevice request, and the like.

FIG. 3 illustrates a diagram showing example components of the mobiledevice 102. As shown, the mobile device 102 may include, but is notlimited to, a user interface manager 302, a tracking device requestmanager 304, a database manager 306, and a tracking manager 308, each ofwhich may be in communication using any suitable communicationtechnologies. It will be recognized that although managers 302-308 areshown to be separate in FIG. 3, any of the managers 302-308 may becombined into fewer managers, such as into a single manager, or dividedinto more managers as may serve a particular embodiment.

As will be explained in more detail below, the mobile device 102includes the user interface manager 302. The user interface manager 302facilitates the user 103 in providing data to and access to data on thetracking system 100 and/or tracking device 106. Further, the userinterface manager 302 provides a user interface by which the user 103can communicate with tracking system 100 and/or tracking device 106 viamobile device 102.

The request manager 304 receives and processes a tracking device requestinput to the mobile device 102 from the user 103 to send to a trackingdevice 106. In one configuration, the user 103 can provide a trackingdevice request for a tracking device 106 via the user interface manager302, and the request manager 304 can process and transmit the trackingdevice request to the tracking device 106 over a second network 110. Inanother embodiment, the request manager 304 can process and provide anynecessary data to the tracking system 100 for processing andtransmitting the tracking device request to other users 105 over a firstnetwork 108. In some configurations, the tracking device request isprovided via user input. Alternatively, the tracking device request istransmitted automatically in response to the mobile device 102determining that a tracking device 106 is out of range (not within athreshold proximity) of the mobile device 102.

The database manager 306 maintains data related to the user 103, thetracking device 106, the tracking device request, or other data that canbe used for communicating with a tracking device 106 and/or providingthe tracking device request to the tracking system 100 for transmittingto one or more tracking devices 106 associated with the user 103.Further, the database manager 306 maintains any information that can beaccessed using any other manager on the mobile device 102.

The tracking manager 308 includes a tracking application (e.g., asoftware application) for communicating with a tracking device 106associated with the user 103. For example, the tracking manager 308 canbe one configuration of a tracking application installed on the mobiledevice 102 that provides the functionality for communicating with atracking device 106 using community mobile devices 104. As shown, thetracking manager 308 may include, but is not limited to, a Bluetooth LowEnergy (BLE) manager 310, a persistence manager 312, a local filesmanager 314, a motion manager 316, a secure storage manager 318, asettings manager 320, a location manager 322, a network manager 324, anotification manager 326, a sound manager 328, a friends manager 330, aphoto manager 332, an authentication manager 334, and a device manager336. Thus, the tracking manager 308 may perform any of the functionsassociated with managers 310-338, described in additional detail below.

The BLE manager 310 can be used to manage communication with one or moretracking devices 106. The persistence manager 312 can be used to storelogical schema information that is relevant to the tracking manager 308.The local files manager 314 can be responsible for managing all filesthat are input or output from the mobile device 102. The motion manager316 can be responsible for all motion management required by thetracking manager 308. The secure storage manager 318 can be responsiblefor storage of secure data, including information such as passwords andprivate data that would be accessed through this sub-system. Thesettings manager 320 can be responsible for managing settings used bythe tracking manager 308. Such settings can be user controlled (e.g.,user settings) or defined by the tracking manager 308 for internal use(e.g., application settings) by a mobile device 102 and/or the trackingsystem 100. The location manager 322 can be responsible for all locationtracking done by the tracking manager 308. For example, the locationmanager 322 can manage access to the location services of the mobiledevice 102 and works in conjunction with other managers to persist data.

The network manager 324 may be responsible for all Internetcommunications from the tracking manager 308. For example, the networkmanager 324 can mediate all Internet API calls for the tracking manager308. The notification manager 326 can be responsible for managing localand push notifications required by the tracking manager 308. The soundmanager 328 can be responsible for playback of audio cues by thetracking manager 308. The friends manager 330 can be responsible formanaging access to contacts and the user's social graph. The photomanager 332 can be responsible for capturing and managing photos used bythe tracking manager 308. The authentication manager 334 can beresponsible for handling the authentication (e.g., sign in or login) ofusers. The authentication manager 334 can also include registration(e.g., sign up) functionality. The authentication manager 334 canfurther coordinate with other managers to achieve registrationfunctionality. The device manager 336 can be responsible for managingthe devices discovered by the tracking manager 308. The device manager336 can further store and/or maintain the logic for algorithms relatedto device discovery and update.

FIG. 4 illustrates a diagram showing example components of a communitymobile device 104. As shown, the community mobile device 104 mayinclude, but is not limited to, a user interface manager 402, a trackingdevice request manager 404, a database manager 406, and a trackingmanager 408, each of which may be in communication using any suitablecommunication technologies. The user interface manager 402, databasemanager 406, and tracking manager 408 illustrated in FIG. 4 may includesimilar features and functionality as the user interface manager 302,database manager 306, and tracking manager 308 described above inconnection with FIG. 3. It will be recognized that although managers402-408 are shown to be separate in FIG. 4, any of the managers 402-408may be combined into fewer managers, such as into a single manager, ordivided into more managers as may serve a particular embodiment.

The user interface manager 402 facilitates the community user 105 of thecommunity mobile device 104 in providing data to and access to data onthe tracking system 100 and/or tracking device 106. Further, the userinterface manager 402 provides a user interface by which the communityuser 105 can communicate with tracking system 100 and/or tracking device106 via mobile device 102.

The request manager 404 transmits a tracking device request to one ormore nearby tracking devices 106. In some configurations, the requestmanager 404 is configured to continuously or periodically scan (e.g.,once per second) nearby areas to determine if there is a tracking device106 within a threshold proximity of the community mobile device 104. Therequest manager 404 can identify the tracking device 106 (e.g., using aunique identifier associated with and transmitted by the tracking device106) and can communicate the identification of the tracking device 106and an associated timestamp to the tracking system 100.

The request manager 404 receives and processes a tracking device requesttransmitted to the community mobile device 104 by the tracking system100. If the tracking device 106 is still within a threshold proximity ofthe community mobile device 104, the request manager 404 transmits thetracking device request to the tracking device 106.

The request manager 404 receives a confirmation signal from the trackingdevice 106 indicating the tracking device 106 has received the trackingdevice request. In response, the request manager 404 transmits theconfirmation signal to the tracking system 100.

In some configurations, the community mobile device 104 may includeadditional features. For example, the community mobile device 104 mayallow a tracking system 100 to snap and download a photo using photofunctionality of the community mobile device 104. In someconfigurations, this may be an opt-in feature by which a community user105 permits a tracking system 100 to take a snap-shot and possiblyprovide a visual image of an area within a threshold proximity of thetracking device 106.

Interaction

FIG. 5A illustrates an interaction diagram for sending a tracking devicerequest from a mobile device 102 to a tracking device 106 leveraging thecapabilities of a community mobile device 104 and a tracking system 100,according to one embodiment.

The tracking system 100 receives or otherwise obtains information from acommunity mobile device 104 of one or more tracking devices 106 within athreshold proximity of the community mobile device 104. The informationreceived from the community mobile device 104 can include a uniquetracking device ID identifying the tracking device 106 and an IDidentifying the community mobile device. The tracking system 100 stores512 the tracking device ID associated with the tracking device 106 inassociation with a community mobile device ID for the community mobiledevice 104 within a threshold proximity of the tracking device 106. Thetracking system 100 can further store additional information associatedwith the community mobile device 104 (e.g., a mobile phone number).

The mobile device 102 sends 514 a tracking device request to thetracking system 100. The tracking device request includes a uniquetracking device ID identifying the tracking device 106 associated withthe tracking device request and identifying one or more actions orfunctions to be implemented by the tracking device 106. In someexamples, the tracking device request can include additional informationassociated with the tracking device 106 (e.g., permissions), informationidentifying the user 103 of the mobile device 102 (e.g., name, username,authentication information), and information associated with the mobiledevice 102 (e.g., a mobile phone number).

The tracking system 100 identifies 516 the community mobile device 104within a threshold proximity of the tracking device 106. The trackingsystem 100 sends 518 the tracking device request to the identifiedcommunity mobile device 104. The tracking device request includes anyinstructions and/or information necessary for the community mobiledevices 104 to send the tracking device request to the tracking device106. If the community mobile devices 104 is still within a thresholdproximity of the tracking device 106 (e.g., if the community mobiledevice 104 is within range of the communication capabilities of thetracking device 106), the community mobile device 104 sends 520 thetracking device request to the tracking device 106. In an embodimentwhere the community mobile device 104 is no longer within a thresholdproximity of the tracking device 106, the community mobile device 104can send an indication to this effect to the tracking system 100, whichin response can identify a second community mobile device 104 previouslydetermined to be within a threshold proximity to the tracking device 106(for instance, a community mobile device 104 determined to be inproximity to the tracking device 106 at an earlier time, from a furtherdistance, and the like), and can forward the tracking device request tothe second community mobile device 104.

The tracking device 106 sends 522 a confirmation signal to the communitymobile device 104 indicating the tracking device request wassuccessfully received. In some embodiments, the confirmation signal isonly sent after or in response to the implementation of the action orfunction specified by the tracking device request. The community mobiledevice 104 sends 524 the confirmation signal to the tracking system 100.The community mobile device 104 can send additional information to thetracking system 100 in the confirmation. For example, the communitymobile device 104 can send a location of the community mobile device 104and a signal strength associated with the tracking device 106 toindicate a level of proximity of the tracking device 106 to the locationof the community mobile device 104. For example, if a signal strength ishigh, the location provided to the tracking system 100 is likely to bemore accurate than a location accompanied by a low signal strength. Thismay provide additional information that the user 103 may find useful indetermining, for example, a precise location of tracking device 106.

The tracking system 100 sends a message to the mobile device 102indicating the tracking device request was successfully received by thetracking device 106 via a community mobile device 104. In addition tothe confirmation indicating the tracking device 106 successfullyreceived the tracking device request, the message can includeinformation associated with the identified community mobile devices 104(e.g., location of the one or more identified community mobile devices104). The message can be a text message, push notification, ring tone,automated voice message, or other response. The message can be displayedto the user 103 via a graphical user interface.

FIG. 5B illustrates an interaction diagram for sending a tracking devicerequest from a mobile device 102 to a tracking device 106 leveraging thecapabilities of a community mobile device 104 and a tracking system 100,according to another embodiment.

The mobile device sends 532 a tracking device request to the trackingsystem 100. The tracking system 100 stores the received tracking devicerequest. The community mobile device 104 sends 536 a tracking device IDof a tracking device determined to be within a threshold proximity tothe community mobile device 104 (for instance, in response to a beaconsignal received 535 from the tracking device 106), along with anindication that the tracking device 106 is within a threshold proximityof the community mobile device 104 (for instance, by including alocation of the community mobile device 104). The tracking system 100identifies 538 the stored tracking device request for the trackingdevice 106 based on the tracking device ID. The tracking system 100sends 540 the pending tracking device request to the identifiedcommunity mobile device 104. If the community mobile device 104 is stillwithin a threshold proximity of the tracking device 106, the communitymobile device 104 sends 542 the tracking device request to the trackingdevice 106.

The tracking device 106 sends 544 a confirmation to the community mobiledevice 104 indicating the tracking device request was successfullyreceived. The community mobile device 104 sends 546 the confirmation tothe tracking system 100. The tracking system 100 sends 548 a message tothe mobile device 102 indicating the tracking device request wassuccessfully received by the tracking device 106 via a community mobiledevice 104.

It should be noted that in some embodiments, the tracking device 106 ofFIG. 1 is a mobile device configured to act as a tracking device, forinstance after the passage of a threshold amount of time withoutreceiving an input from a user, without receiving a communication fromthe tracking system, without detecting movement, or the like. In suchembodiments, the mobile device 102 is any connected device (e.g.,personal computer, laptop, tablet, etc.) capable of communicating withthe tracking system 100 via the first network 108. In such embodiments,the tracking device instructions can be sent to the mobile device actingas a tracking device, enabling the mobile device to be “rung” or tootherwise play or display a notification from another mobile device oranother tracking device, beneficially enabling an owner of the mobiledevice to locate the mobile device. In some embodiments, the mobiledevice can be marked as lost, for instance in response to a designationof the mobile device as lost by the owner of the mobile device, inresponse the passage of a threshold amount of time without acommunication between the tracking system and the mobile device, inresponse to the passage of a threshold amount of time without a detectedmovement of the mobile device, or based on any other suitable factors.In some embodiments, a mobile device configured to act as a trackingdevice can emit period Bluetooth beacon signals. In such embodiments,when a second user with a community mobile device comes within athreshold proximity of the mobile device configured as a trackingdevice, the community mobile device of the second user can receive theBluetooth beacon signal, and can report the location of the mobiledevice to the tracking system. In turn, the tracking system can providea notification to the user that the mobile device configured to act as atracking device has been found, the location of the mobile deviceconfigured to act as a tracking device, and the like.

In some embodiments, a mobile device configured to act as a trackingdevice can emit a notification in response to an input by a user at thetracking device. For instance, a user can interact with a button,switch, dial, displayed interface, or other interface at the trackingdevice, which can provide configuration instructions to the mobiledevice to ring. Such embodiments, beneficially allow a user to locate amobile device from a tracking device. In some embodiments, the trackingdevice can, in response to a communication received from the mobiledevice or a lack thereof, emit one of a plurality of notifications. Forexample, a tracking device can emit a first ringtone in response tofailing to receive, from the mobile device, a response to configurationinstructions sent by the tracking device. Continuing with this example,the tracking device can emit a second ringtone if the tracking device iscommunicatively coupled with the mobile device, can emit a thirdringtone in response to detecting the mobile device but being unable tocommunicatively couple to the mobile device, and emit a fourth ringtonein response to detecting the mobile device but before attempting tocommunicatively couple to the mobile device, can emit a fifth ringtonein response to actively attempting to communicatively couple to themobile device, or any combination or sub-combination thereof.

Additional Considerations

The foregoing description of the embodiments of the invention has beenpresented for the purpose of illustration; it is not intended to beexhaustive or to limit the invention to the precise forms disclosed.Persons skilled in the relevant art can appreciate that manymodifications and variations are possible in light of the abovedisclosure.

Any of the devices or systems described herein can be implemented by oneor more computing devices. A computing device can include a processor, amemory, a storage device, an I/O interface, and a communicationinterface, which may be communicatively coupled via communicationinfrastructure. Additional or alternative components may be used inother embodiments. In particular embodiments, a processor includeshardware for executing computer program instructions by retrieving theinstructions from an internal register, an internal cache, or othermemory or storage device, and decoding and executing them. The memorycan be used for storing data or instructions for execution by theprocessor. The memory can be any suitable storage mechanism, such asRAM, ROM, flash memory, solid state memory, and the like. The storagedevice can store data or computer instructions, and can include a harddisk drive, flash memory, an optical disc, or any other suitable storagedevice. The I/O interface allows a user to interact with the computingdevice, and can include a mouse, keypad, keyboard, touch screeninterface, and the like. The communication interface can includehardware, software, or a combination of both, and can provide one ormore interfaces for communication with other devices or entities.

Some portions of this description describe the embodiments of theinvention in terms of algorithms and symbolic representations ofoperations on information. These algorithmic descriptions andrepresentations are commonly used by those skilled in the dataprocessing arts to convey the substance of their work effectively toothers skilled in the art. These operations, while describedfunctionally, computationally, or logically, are understood to beimplemented by computer programs or equivalent electrical circuits,microcode, or the like. Furthermore, it has also proven convenient attimes, to refer to these arrangements of operations as modules, withoutloss of generality. The described operations and their associatedmodules may be embodied in software, firmware, hardware, or anycombinations thereof.

Any of the steps, operations, or processes described herein may beperformed or implemented with one or more hardware or software modules,alone or in combination with other devices. In one embodiment, asoftware module is implemented with a computer program productcomprising a computer-readable medium containing computer program code,which can be executed by a computer processor for performing any or allof the steps, operations, or processes described.

Embodiments of the invention may also relate to an apparatus forperforming the operations herein. This apparatus may be speciallyconstructed for the required purposes, and/or it may comprise ageneral-purpose computing device selectively activated or reconfiguredby a computer program stored in the computer. Such a computer programmay be stored in a non-transitory, tangible computer readable storagemedium, or any type of media suitable for storing electronicinstructions, which may be coupled to a computer system bus.Furthermore, any computing systems referred to in the specification mayinclude a single processor or may be architectures employing multipleprocessor designs for increased computing capability.

Embodiments of the invention may also relate to a product that isproduced by a computing process described herein. Such a product maycomprise information resulting from a computing process, where theinformation is stored on a non-transitory, tangible computer readablestorage medium and may include any embodiment of a computer programproduct or other data combination described herein.

Finally, the language used in the specification has been principallyselected for readability and instructional purposes, and it may not havebeen selected to delineate or circumscribe the inventive subject matter.It is therefore intended that the scope of the invention be limited notby this detailed description, but rather by any claims that issue on anapplication based hereon. Accordingly, the disclosure of the embodimentsof the invention is intended to be illustrative, but not limiting, ofthe scope of the invention, which is set forth in the following claims.

What is claimed is:
 1. A tracking device comprising: a transmitterconfigured to broadcast a beacon signal identifying the tracking deviceat a first beacon frequency; a receiver configured to receive, from acommunity mobile device, a tracking device request comprisingconfiguration instructions identifying a second beacon frequency, thetracking device request transmitted by the community mobile device inresponse to the community mobile device receiving the beacon signalbroadcast by the transmitter; and a controller configured to change afrequency of the beacon signal broadcast by the transmitter from thefirst beacon frequency to the second beacon frequency identified by theconfiguration instructions.
 2. The tracking device of claim 1, whereinthe transmitter is further configured to transmit a confirmation signalto the community mobile device, the confirmation signal indicating theconfiguration instructions were received by the tracking device.
 3. Thetracking device of claim 1, wherein the transmitter is configured, inresponse to the configuration instructions, to periodically broadcastthe beacon signal at an interval indicated by the second beaconfrequency.
 4. The tracking device of claim 1, wherein the receiver isfurther configured to receive second configuration instructionscomprising an identifier of a mobile device to add to a list of verifiedmobile devices stored by the tracking device, and the controller isfurther configured to store, in a memory of the tracking device, theidentifier of the mobile device in the list of verified mobile devicesstored by the tracking device.
 5. The tracking device of claim 4,wherein the community mobile device from which the tracking devicerequest received is a verified community mobile device.
 6. The trackingdevice of claim 1, wherein the tracking device request further comprisesan identifier of the community mobile device from which the trackingdevice request was received, and the controller is further configured tocompare the identifier of the community mobile device to a list ofverified mobile devices stored by the tracking device to determine thatthe community mobile device is permitted to configure the trackingdevice.
 7. The tracking device of claim 1, wherein the community mobiledevice receives instructions for transmitting the tracking devicerequest from a tracking server, and the community mobile devicetransmits the tracking device request in response to the instructionsfrom the tracking server.
 8. A method comprising: broadcasting, by atransmitter of a tracking device, a beacon signal identifying thetracking device at a first beacon frequency; receiving, at the trackingdevice from a community mobile device, a tracking device requestcomprising configuration instructions identifying a second beaconfrequency, the tracking device request transmitted by the communitymobile device in response to the community mobile device receiving thebeacon signal broadcast by the transmitter; and in response to receivingthe tracking device request, changing a frequency of the beacon signalbroadcast by the tracking device from the first beacon frequency to thesecond beacon frequency identified by the configuration instructions. 9.The method of claim 8, further comprising transmitting a confirmationsignal to the community mobile device, the confirmation signalindicating the configuration instructions were received by the trackingdevice.
 10. The method of claim 8, further comprising periodicallybroadcasting the beacon signal at an interval indicated by the secondbeacon frequency in response to the configuration instructions.
 11. Themethod of claim 8, further comprising: receiving second configurationinstructions comprising an identifier of a mobile device to add to alist of verified mobile devices stored by the tracking device; andstoring, in a memory of the tracking device, the identifier of themobile device in the list of verified mobile devices stored by thetracking device.
 12. The tracking device of claim 11, wherein thecommunity mobile device from which the tracking device request receivedis a verified community mobile device.
 13. The tracking device of claim8, wherein the tracking device request further comprises an identifierof the community mobile device from which the tracking device requestwas received, the method further comprising: comparing the identifier ofthe community mobile device to a list of verified mobile devices storedby the tracking device to determine that the community mobile device ispermitted to configure the tracking device.
 14. The tracking device ofclaim 8, wherein the community mobile device receives instructions fortransmitting the tracking device request from a tracking server, and thecommunity mobile device transmits the tracking device request inresponse to the instructions from the tracking server.
 15. Anon-transitory computer-readable storage medium storing executablecomputer instructions that, when executed by a hardware processor,perform steps comprising: broadcasting a beacon signal identifying atracking device at a first beacon frequency; receiving, from a communitymobile device, a tracking device request comprising configurationinstructions identifying a second beacon frequency, the tracking devicerequest transmitted by the community mobile device in response to thecommunity mobile device receiving the beacon signal broadcast by thetransmitter; and changing a frequency of the beacon signal broadcast bythe tracking device from the first beacon frequency to the second beaconfrequency identified by the configuration instructions in response toreceiving the tracking device request.
 16. The computer-readable storagemedium of claim 15, wherein the instructions, when executed, performfurther steps comprising: transmitting a confirmation signal to thecommunity mobile device, the confirmation signal indicating theconfiguration instructions were received by the tracking device.
 17. Thecomputer-readable storage medium of claim 15, wherein the instructions,when executed, perform further steps comprising: periodicallybroadcasting the beacon signal at an interval indicated by the secondbeacon frequency in response to the configuration instructions.
 18. Thecomputer-readable storage medium of claim 15, wherein the instructions,when executed, perform further steps comprising: receiving secondconfiguration instructions comprising an identifier of a mobile deviceto add to a list of verified mobile devices stored by the trackingdevice; and storing, in a memory of the tracking device, the identifierof the mobile device in the list of verified mobile devices stored bythe tracking device.
 19. The computer-readable storage medium of claim18, wherein the community mobile device from which the tracking devicerequest received is a verified community mobile device.
 20. Thecomputer-readable storage medium of claim 15, wherein the trackingdevice request further comprises an identifier of the community mobiledevice from which the tracking device request was received, and theinstructions, when executed, perform further steps comprising: comparingthe identifier of the community mobile device to a list of verifiedmobile devices stored by the tracking device to determine that thecommunity mobile device is permitted to configure the tracking device.